@rubytech/create-maxy 1.0.761 → 1.0.763

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/create-maxy",
-  "version": "1.0.761",
+  "version": "1.0.763",
   "description": "Install Maxy — AI for Productive People",
   "bin": {
     "create-maxy": "./dist/index.js"

package/payload/platform/neo4j/schema.cypher

@@ -802,6 +802,56 @@ FOR (tc:ToolCall) REQUIRE tc.callId IS UNIQUE;
 CREATE INDEX tool_call_account_started IF NOT EXISTS
 FOR (tc:ToolCall) ON (tc.accountId, tc.startedAt);
 
+// ----------------------------------------------------------
+// Component — Task 815 admin-resume rehydration.
+//
+// Every render-component event emitted on an assistant turn
+// produces one Component node linked to its parent Message via
+// (Message)-[:HAS_COMPONENT]->(Component). The agent's narrative
+// text stays on Message.content; component name + data JSON +
+// position-relative-to-text live here. Sibling-node design (not
+// JSON-on-Message) avoids Neo4j's 128KB property soft-limit when
+// document-editor bodies are large.
+//
+// Atomicity: persisted in the same Cypher transaction as the
+// parent Message — no orphan Component possible. Reader is a
+// single round-trip via OPTIONAL MATCH + collect (sort-before-
+// collect: WITH m, c ORDER BY c.ordinal ASC, then collect).
+//
+// Properties:
+//   componentId  — UUID, primary key
+//   conversationId / accountId / messageId — denormalised for
+//     account-scoped reads and cross-account isolation audits
+//   name         — component name (document-editor, action-buttons,
+//                   single-select, etc.)
+//   data         — JSON-encoded payload string. Validated structurally
+//                   on read (parseable, non-null object); per-component
+//                   schema validation lives in validateComponentData.
+//   ordinal      — 0-indexed sequence within the parent Message,
+//                   tiebreak for components with the same textOffset.
+//   textOffset   — length of Message.content at the moment this
+//                   component arrived in the SSE stream. Reader uses
+//                   it to interleave text-runs and components when
+//                   reconstructing events: AdminEvent[].
+//   submitted    — true once a PERSISTENT_COMPONENT (action-list,
+//                   document-editor, rich-content-editor, grid-editor)
+//                   was submitted by the user. Server-side detection
+//                   of `_componentDone:true` user turns flips this.
+//   submittedAt  — datetime when submitted=true was set (null otherwise)
+//   createdAt    — datetime when the component was persisted
+//
+// (:Message)-[:HAS_COMPONENT]->(:Component)
+// ----------------------------------------------------------
+
+CREATE CONSTRAINT component_id_unique IF NOT EXISTS
+FOR (c:Component) REQUIRE c.componentId IS UNIQUE;
+
+CREATE INDEX component_message IF NOT EXISTS
+FOR (c:Component) ON (c.messageId);
+
+CREATE INDEX component_account IF NOT EXISTS
+FOR (c:Component) ON (c.accountId);
+
 // ----------------------------------------------------------
 // :Trashed — Task 576 soft-delete primitive.
 //

package/payload/platform/plugins/docs/references/platform.md

@@ -65,7 +65,7 @@ There is no dashboard, no settings panel, no menus. Everything is done through c
 
 The chat input auto-grows as you type — it expands to fit your message and shrinks back when you delete text. You can also drag the resize handle above the input to set a custom height.
 
-The admin interface is a three-pane layout: a sidebar on the left with your brand mark, navigation (Chat, Projects, Artefacts), and your recent conversations; the chat in the middle; and an artefact pane on the right that opens when you select a document, holding it side-by-side with the conversation that referenced it. The sidebar's nav rows swap the list view in place — Chat shows recent conversations, Projects shows your active work projects, and Artefacts lists every document the agent has created or ingested. Click an artefact row to open it in the right pane. On wider screens (>1280px) all three panes are visible. The sidebar narrows at 1280px, the artefact pane hides at 1080px, and the sidebar collapses to a 56px icon rail at 820px. On phones (<640px) the sidebar slides in as a drawer from the left when you tap the menu icon in the chat header.
+The admin interface is a three-pane layout: a sidebar on the left with your brand mark, navigation (Chat, Projects, Artefacts), and your recent conversations; the chat in the middle; and an artefact pane on the right that opens when you select a document or open Browser, Data, or Graph from the menu — holding the surface side-by-side with the conversation so the chat stays live while you work in it. The sidebar's nav rows swap the list view in place — Chat shows recent conversations, Projects shows your active work projects, and Artefacts lists every document the agent has created or ingested. Click an artefact row to open it in the right pane. The chat / artefact divider is drag-resizable — drag the line between the columns to make either side wider; double-click it to reset. Your chosen width is remembered across reloads. On wider screens (>1280px) all three panes are visible. The sidebar narrows at 1280px, the artefact pane hides at 1080px (Browser, Data, and Graph then open as full-window pages instead), and the sidebar collapses to a 56px icon rail at 820px. On phones (<640px) the sidebar slides in as a drawer from the left when you tap the menu icon in the chat header.
 
 Page titles are brand-aware: the browser tab shows your product name (e.g. `Real Agent` instead of `Maxy`) on every shell — chat, graph, and data — so a non-default brand never leaks the default name in tab strips or browser history.